home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ShareWare OnLine 2
/
ShareWare OnLine Volume 2 (CMS Software)(1993).iso
/
infor
/
ethernet.zip
/
ETHERNET.DOC
Wrap
Text File
|
1993-03-13
|
19KB
|
450 lines
ETHERNET FOR OS/2
Version 1.0
July, 1991
This document is for support people and users of Ethernet-related
products on OS/2 Extended Edition. An understanding of OS/2,
Communications Manager, and a basic familiarity with LAN concepts
is assumed.
In this document, the term Ethernet shall be used to describe both
Ethernet/DIX version 2 and IEEE 802.3 protocols. OS/2 shall describe
OS/2 EE version 1.2 or higher.
Currently the following adapters are supported for use with OS/2:
IBM PS/2 Adapter/A for Ethernet Networks
3Com Etherlink II Network Adapter
3Com Etherlink/MC Network Adapter
Western Digital EtherCard PLUS Network Adapter
Western Digital EtherCard PLUS/A Network Adapter
Ungermann-Bass NIUpc Network Adapter
Ungermann-Bass NIUps Network Adapter
GENERAL INFORMATION
Ethernet is not like token ring or some other networks that will
either continue to function or begin beaconing when a physical
connection is broken. Ethernet is a bus topology. It is daisy-
chained together and terminated on both ends. The chain must
always be intact, or the whole network will go down.
Ethernet is based on carrier sense multiple access with collision
detection (CSMA/CD) as its methodology. Each adapter "listens" on
the network for a period of inactivity, and when it finds an available
time, it puts its packet out on the network. If two packets are put
out on the network at the same time, it may cause a collision. The
adapters that sent the packets are notified of the collision, this
causes them to wait a random amount of time before attempting to send
another packet. During this time, other stations may transmit. This
method, though it might not appear so, is very efficient. However,
on large networks with high percentages of network utilization, problems
can occur.
Two network protocols are supported for Ethernet --
o Ethernet DIX (Digital Intel Xerox) Ver 2.0
o IEEE 802.3
The major difference between the two is the encoding of the frames.
Neither offers better performance than the other.
**NOTE:**
These protocols are INCOMPATIBLE. Only one or the other may exist
on any Ethernet network. Communications Manager defaults to DIX, while
Lan Support Program 1.2 defaults to 802.3. Be careful when configuring
a network with both OS/2 and DOS machines.
There are three files that control Ethernet settings. They are:
o PROTOCOL.INI - Tells what kind of adapter is being used and the
parameters that are associated with that adapter.
Resides in \CMLIB.
o CONFIG.SYS - Tells what device drivers to load and what the
Communications Manager file is.
o \CMLIB\*.CFG - Tells which adapter is 0 or 1, and what values the
various protocol parameters in the network layers
will be within Communications Manager.
ADAPTER INSTALLATION
1. Install the adapter and run Automatic Configuration or Set Config-
uration as usual. The ADF should be supplied with the card.
Record the Interrupt Level (IRQ), the IOBase address, and the
RAM address if applicable. The settings here will override those
in the PROTOCOL.INI file, but PROTOCOL.INI should match up with these
values.
2. If a token ring card co-exists in the machine, make the Ethernet adapter
primary by setting the token ring to alternate.
3. The following adapter combinations in the same machine will not work:
o Two Western Digital cards
o Two Ungermann-Bass cards
o An Ethernet adapter and a PC Network adapter
CABLING INSTRUCTIONS
This is one of the most critical parts of properly setting up an Ethernet
network. There are three types of Ethernet cabling: thin Ethernet,
standard (thick) Ethernet, and unshielded twisted pair. This document
will only cover thin Ethernet.
Thin Ethernet (sometimes called Cheapernet) uses RG58 A/U cables. These
cables are attached to T connectors which are attached at the card via
1 of 2 methods, either through the BNC connector (the round, coaxial
connector) directly on the card, or to a BNC connector on a network
transceiver box which is then connected via the AUI, (the pin connector)
on the card. Most thin Ethernet connections will be done without the
AUI. Ungermann-Bass is the exception in that it uses the AUI
connection exclusively.
o Cable Installation for 3Com, Western Digital, and IBM Cards
To install the cable you will need one T connector for each adapter, one
piece of RG58 A/U cable to run between each machine, and two 50 ohm
terminators.
1. Put the T connector on the BNC connection on the card.
2. Place one terminator on one side of the T.
3. Attach a cable to the other side.
4. Place a T connector on the next card, hooking up one side with the
cable from the previous adapter, and plugging in a cable on the other
side.
5. Continue daisy chaining cable from machine to machine until the
last adapter has been reached, then plug in the other terminator.
o Cable Installation for Ungermann-Bass
Ungermann-Bass makes use of a Network Transceiver box, into which the T
connector is already built. To connect the box to the adapter,
simply connect the AUI cable between the two. Then, using RG58 A/U cable,
daisy chain the transceiver boxes together as explained above in the
3Com and Western Digital instructions. Make sure the line is properly
terminated with two 50 ohm terminators.
o Maximum length of Ethernet
On large networks (over 100 stations), you will need to implement signal
strengthening devices called repeaters. The maximum cable segment length
between repeaters is 300 meters. The total network span cannot exceed
925 meters. Up to 100 LAN stations are supported per segment. 1024 LAN
stations can be supported on the network.
o Ethernet vs. DFT cable
Although DFT cable (RG62 A/U) is thicker but otherwise similar to
RG58 A/U, it is unacceptable as Ethernet cable.
ADAPTER DEVICE DRIVER INSTALLATION FOR OS/2.
You must have OS/2 EE 1.2 or higher with Communications Manager and
LAN Services support installed.
1. Use the Basic Configurations Services function to create the
Communications Manager Configuration (.CFG) file. This file is
needed by LAN Requester. Select the following as they appear.
A. LAN Services plus any CM features.
B. According to your requirements, select either LAN Requester or
LAN Server.
C. Adapter Type - Select the appropriate adapter. NOTE: If you
are using the IBM Ethernet Adapter and it is not displayed,
select Western Digital "Ethercard PLUS/A".
D. Universal local LAN Adapter address - select YES. If NO is
selected, ensure that the address used is not in conflict with
an address on the network. Check with the network administrator
for the proper selection.
2. Complete the installation of the OS/2 software.
3. Restart the computer, the NETWKSTA.SYS device driver will fail until
the setup step described below are completed.
4. If you are using the IBM Ethernet Adapter complete the following
sequence (if you are using another adapter skip to step 5):
A. If you do not have it, obtain a copy of the IBM Ethernet
Adapter/A options diskette. (IBMers can get a copy by sending
a note to D940U04 AT AUSVM1 or ROB AT BCRVM5. Customers can
ask their SE to acquire the latest one for them.)
B. Select the DOS mode of OS/2.
C. Insert the disk into drive A: and type INSTALL at the A: prompt.
D. Follow the instructions on the screen.
5. From the Communications Manager screen choose Advanced.
6. Select Option 4. Configuration.
7. Press Enter when the Specify Configuration File Name pop-up appears.
8. Select Option 6. LAN feature profiles.
9. Choose the Ethernet Adapter to be adapter 0. If there are two Ethernet
adapters, it does not matter which is chosen as adapter 0.
10. Select IEEE 802.2 and Change. There will be a list of adapters displayed,
select the one you are using. If you are using the IBM Ethernet Adapter
and it is not displayed, select Western Digital EtherCard PLUS/A Network
Adapter. With some adapters you will be shown a list of shared RAM
addresses, choose the default unless you have specified a different shared
RAM address when configuring the machine. If in doubt, use the reference
disk to verify the address.
11. You now have a pop-up asking you to select either Ethernet DIX Version
2.0 or IEEE 802.3. You must ensure that the same protocol is chosen for
every machine on the network. The major difference between the two is the
frame structure. Neither one offers major advantages over the other, but
the two protocols are mutually exclusive.
12. After choosing the protocol, you will be in the Network Profile selection
menu. Unless you have special reasons to adjust the parameters, just
press Enter to pass through the screens.
13. Now you should be at the LAN Profile Configuration screen. Select Netbios
and Change and press enter. All the defaults should be OK, unless you
have some reason to customize, just press enter on both screens.
14. Press F3 to return to the Communications Manager Configuration Menu.
15. Select Verify from the action bar, then select Run Verify from the pull-
down that appears.
16. When the message "Verification of the configuration file is complete"
appears, restart the system. If the file does not verify properly,
check the messages for further instructions.
MODIFYING PROTOCOL.INI
When you configure the machine, the default PROTOCOL.INI will be created
for you. You must modify it to suit your needs. If you have used the
IBM Ethernet adapter install diskette, you will not need to modify
PROTOCOL.INI as it has already been done for you.
The following PROTOCOL.INI is for a PS/2 with an IBM Ethernet Adapter.
To change it to a Western Digital, you would change the "Bindings" statement
to WDMAC, for Ungermann-Bass-- UBMAC, and so on. Ensure that interrupts
and RAM addresses match up with those that were referenced, if appropriate.
; --------------------- Protocol Manager Definition -----------------------
╒PROTOCOL_MANAGER■
DriverName = PROTMAN$
; ------------------- IBM ETHERAND Protocol Definition --------------------
╒ETHERAND■
DriverName = OS2EE$
Bindings = IBMAC
; The modules listed below are valid choices for the Bindings field.
;
; (1) TCMAC2 - 3Com Micro Channel Adapters
; (2) TCMAC - 3Com IBM PC-AT Adapters
; (3) WDMAC - Western Digital Micro Channel and IBM PC-AT Adapters
; (4) UBMAC - Ungermann-Bass Micro Channel and IBM PC-AT Adapters
; (5) IBMAC - IBM PS/2 Adapter/A for Ethernet Networks
;
; NOTE: If you choose UBMAC, please check the AdapterType
; definition to ensure that it is correct for your
; adapter.
; ------------------- 3Com Network Adapter Definition ---------------------
╒TCMAC2■
DriverName = ELNKMC$
MaxTransmits = 10
╒TCMAC■
DriverName = ELNKII$
Interrupt = 3
IOAddress = 0x300
DMAChannel = 3
MaxTransmits = 10
Transceiver = Onboard
; -------------- Western Digital Network Adapter Definition ---------------
╒WDMAC■
DriverName = MACWD$
IRQ = 3
RamAddress = 0xC400
IOBase = 0x280
ReceiveBuffers = 16
ReceiveChains = 16
MaxRequests = 10
MaxTransmits = 10
ReceiveBufSize = 256
; -------------- Ungermann-Bass Network Adapter Definition ----------------
╒UBMAC■
DriverName = UBMAC$
AdapterType = NIUps
MemoryWindow = 0xD8000
IO_Port = 0x350
IRQ_Level = 4
MaxRequests = 10
MaxTransmits = 10
ReceiveBufSize = 600
MaxMulticast = 20
UseReceiveChain = Never
; -------------- IBM PS/2 Adapter for Ethernet Networks ---------------
╒IBMAC■
DriverName = MACETH$
IRQ = 10
RamAddress = 0xD800
IOBase = 0x200
ReceiveBuffers = 16
ReceiveChains = 16
MaxRequests = 10
MaxTransmits = 10
ReceiveBufSize = 256
;**** END OF FILE ****
MODIFYING CONFIG.SYS
Your CONFIG.SYS file should be automatically configured when you install the
machine. The following statements are the minimum needed to run an Ethernet
network properly:
DEVICE=C:\CMLIB\LANDD.SYS
DEVICE=C:\CMLIB\PROTMAN.OS2 /I:C:\CMLIB
DEVICE=C:\CMLIB\<drivername>.OS2
DEVICE=C:\CMLIB\ETHERDD.SYS CFG=C:\CMLIB\<config file name>.CFG
DEVICE=C:\CMLIB\NETBDD.SYS CFG=C:\CMLIB\<config file name>.CFG
RUN=C:\CMLIB\ACSEPSYS.EXE
RUN=C:\CMLIB\NETBIND.EXE
CONFIGURING TWO ETHERNET ADAPTERS
a) You can use two IBM or 3Com adapters in the same machine but only
one Western Digital or Ungermann-Bass (there is no secondary NDIS
driver and a renamed copy of the driver is not valid). You can also
use two Ethernet adapters of different makes.
b) You need a command in CONFIG.SYS for the NDIS driver for each
adapter. These commands must be consecutive, primary first.
c) A driver for the second IBM adapter is provided (MACETH2.OS2). For
the 3Com adapter, just list ELNKMC.OS2 a second time.
d) By putting a comma (,) in front of the entry for the BINDINGS = field,
for example, BINDINGS = ,WDMAC. The sequence determines which is
primary and which is alternate (primary is first).
e) In the Communications Manager "LAN Profile Configuration" screen, choose
adapter 1 instead of 0 and follow the instructions Adapter Installation
instructions. If you're using two IBM Ethernet adapters, choose the
3Com/Etherlink MC adapter for your second choice.
TROUBLE SHOOTING
Errors in opening the adapter
If you have problems you suspect to be adapter related, there are two
ways to test the card. First, you should run the diagnostics that came
with the card, though they can be somewhat unreliable. Then conduct a
loopback test by placing two 50 ohm terminators on a T connector and
then placing the T connector on the card. Do not place a 50 ohm
terminator directly on the BNC connection of the adapter. You may
however, use a 25 ohm adapter if you wish to terminate the card in
such a way. By terminating the card, you can isolate adapter problems
from network problems.
Failure to bind
These are the most common types of failures and also the hardest to
track down. Should a machine fail to bind, there are probably errors
in PROTOCOL.INI or CONFIG.SYS. Check that the entry in the bindings
statement in PROTOCOL.INI is appropriate to the adapter type. Verify
that the proper <fn>.OS2 file is pointed to in CONFIG.SYS. Verify
spelling. Check that all files pointed to are in their proper
directories and that the filenames are spelled correctly. After that
consult your local Ethernet guru. If you are the local Ethernet guru
you're on your own.
Boot time failures
If you get an 06421 error at boot time, the IBM Ethernet adapter is not
properly plugged into the network. Check the connections to the
adapter.
Hangs
Hangs can be caused by Ethernet adapters. On some cards, there is a
jumper setting for BNC or AUI connection. If this is improperly
set, it will hang the machine.
Starting Lan requester
When starting the LAN requester service, the machine may hang
because of improper configuration in Communications Manager
or a difference in protocol (IEEE 802.3 vs. Ethernet DIX).
Intermittent errors
Intermittent errors are usually hardware related. There are, of course,
exceptions to the rule, but shorts in cables, adapters, BNC and AUI
connections are more often the source of the problem than is software.
Broken and improperly installed terminators can be the source of these
kinds of errors, as can terminators of the wrong impedance. The best way
to isolate these problems is, if possible, to isolate that portion of the
network by terminating a portion of the line and attempting to recreate
the failure. Expand or decrease the size of the terminated line until
you can isolate the area of the failure. There is a high probability
that the problem exists with a cable, terminator, or T-connector in that
area.
CAVEATS
o Two Ungermann-Bass adapters CANNOT exist in the same machine.
o Two Western Digital adapters CANNOT exist in the same machine.
o A PC Network Adapter and an Ethernet Adapter CANNOT exist in the same
machine.
o If there is a 3Com Ethernet adapter, token ring adapter, and an SDLC card
in same machine, the 3Com IRQ level has to be set on int 9 or else a
CONFIS.SYS error will be generated.
o Watch out for defaults with DOS and OS/2 machines on the same net, OS/2
defaults to ETHERNET/DIX, DOS to 802.3.
o When using the 8209 bridge:
Make sure frame sizes on token ring side are set to 1496.
Use 802.3 mode.
o If communicating with non-IBM products on Ethernet, you may have to perform
bit-reversal on each byte of the adapter address. See the Communications
Manager Systems Administrator's Guide for details.
o When using a 486 machine with 3Com adapters, you must use the 3C523B
adapter.
o When using Ungermann-Bass make sure the adapter type is correct in
PROTOCOL.INI, NIUps for Micro-Channel and NIUpc for AT bus.
o When configuring an AT, the user must be very careful to insure that
the IO Base and RAM address defaults are not in conflict with other
_____________________________________________________________________________
This document blatantly takes much of its format and content from
Julian Over's LSP 1.2 document, and I am grateful for his permission to
do so. I also am indebted to David Young, Mark Simpson, Janice Manley,
and the LAN and Communications Manager 2.5 support groups for their help
in preparing this document.
Any questions, comments, suggestions, corrections, lucid insights, or
unsolicited testimonials may be sent to the author, Heath Newburn via
D940U04 at AUSVM1.